Fix #14487: FP duplicateBranch with empty macro#8481
Merged
ludviggunne merged 2 commits intocppcheck-opensource:mainfrom Apr 27, 2026
Merged
Fix #14487: FP duplicateBranch with empty macro#8481ludviggunne merged 2 commits intocppcheck-opensource:mainfrom
ludviggunne merged 2 commits intocppcheck-opensource:mainfrom
Conversation
|
danmar
approved these changes
Apr 25, 2026
Collaborator
danmar
left a comment
danmar
left a comment
There was a problem hiding this comment.
I can live with the false negatives when no such macro is used.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
My reasoning here is that a single semicolon most likely is a result of an empty macro expansion. I can't think of a case where one would put a single semicolon where it would make sense to warn.